Tighten up some parts of the label specification #295
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While I was implementing this over at
ome-zarr-models
, and it's in my head, I put together a series of clarifications and improvements to the labels part of the specification. I'm opening this now while it's fresh in my head so I don't forget, but this shouldn't be merged into 0.5, and should wait until #276 is resolved.Changes:
uint128
is not an acceptable data type, where "MUST be an integer data type" could allow that. (I know that in practice the data types are limited by those in the zarr spec, but better to be expclicit than implicit)